Downgrading a module without any question

Is there a way to downgrade a module (downgrade() or downgradeShare()) without having the dxl asking if you want to save the module.

I found a way to do this when closing a module:
setTriggerState_ (false)
close(m, false)
setTriggerState_ (true)

but this does not work for downgrading a module:
setTriggerState_ (false)
downgrade(m)
setTriggerState_ (true)

setTriggerState_ (false)
downgradeShare(m)
setTriggerState_ (true)

Any suggestion?
phenri - Thu Mar 24 13:33:07 EDT 2011

Re: Downgrading a module without any question
llandale - Thu Mar 24 14:46:22 EDT 2011

close(m, false) should close without question; you don't need the triggerStatus stuff.

And besides, the triggerState stuff has no effect on standard users anyway; you can turn off triggerState but the triggers still fire.

But I don't know about downgrading, but you could take a little more time and close it then read it.

There is an "unsaved(mod)" command; perhaps close and open when true but downgrade when false.

  • Louie

Re: Downgrading a module without any question
phenri - Fri Mar 25 09:11:50 EDT 2011

llandale - Thu Mar 24 14:46:22 EDT 2011
close(m, false) should close without question; you don't need the triggerStatus stuff.

And besides, the triggerState stuff has no effect on standard users anyway; you can turn off triggerState but the triggers still fire.

But I don't know about downgrading, but you could take a little more time and close it then read it.

There is an "unsaved(mod)" command; perhaps close and open when true but downgrade when false.

  • Louie

I did try to close and re-open the module and it does work.
Still the problem is that I am redirecting the Edit->Edit Mode->Read-Only menu to my own dxl, and doing so have the following unwanted behavior compared to the default DOORS behavior:
  • The current object is reset
  • The keyboard focus is set back to the Toolbar or menu
  • Seeing the module closing and re-opening is anoying considering the default DOORS behavior just downgrades the module (you don't see the module window flashing on the screen).

Re: Downgrading a module without any question
Mathias Mamsch - Fri Mar 25 12:21:16 EDT 2011

phenri - Fri Mar 25 09:11:50 EDT 2011
I did try to close and re-open the module and it does work.
Still the problem is that I am redirecting the Edit->Edit Mode->Read-Only menu to my own dxl, and doing so have the following unwanted behavior compared to the default DOORS behavior:

  • The current object is reset
  • The keyboard focus is set back to the Toolbar or menu
  • Seeing the module closing and re-opening is anoying considering the default DOORS behavior just downgrades the module (you don't see the module window flashing on the screen).

Would you care to elaborate a little bit on what you are trying to do? Reading this other post. You seem to be doing a couple of modifications to the DOORS client directly, which will force the user to comply to a change management process. I guess it would be interesting to hear about the means and ends, that you took/will take, to do so.

While this might be achivable, you should think about if you really want to help people remember to follow the process or force them to do so. I don't think that DOORS will give you enough possibilities to make this robust against willing manipulation. Maybe the time would be better invested in helping people follow the process and training them to do so?

Just some thoughts, regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Downgrading a module without any question
phenri - Mon Mar 28 11:06:56 EDT 2011

Mathias Mamsch - Fri Mar 25 12:21:16 EDT 2011
Would you care to elaborate a little bit on what you are trying to do? Reading this other post. You seem to be doing a couple of modifications to the DOORS client directly, which will force the user to comply to a change management process. I guess it would be interesting to hear about the means and ends, that you took/will take, to do so.

While this might be achivable, you should think about if you really want to help people remember to follow the process or force them to do so. I don't think that DOORS will give you enough possibilities to make this robust against willing manipulation. Maybe the time would be better invested in helping people follow the process and training them to do so?

Just some thoughts, regards, Mathias


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

You are right that I am trying to FORCE people to enter a PR# to any changes they do. We have our own custom Save DXL that will update the Change Reason of each modified/deleted/undeleted object when a user is saving a module.

It might be appropriate here to mention this DOORS Client customisation was already done by another company from which we bought the IP of a certified project. So we have inherited this cutomisation and it did not work correctly in our own DOORS environement, therefore we had to get into it and modify it.

After I fixed and ported every DXL correctly, I started to see some holes and design deficiencies and tried to fix them the best I can, hence my 3 posts on this forum.

Even though I am trying to change these DXLs the least possible, I am willing to try better ways to do the same things, like trigger by exemple, if it fixes these deficinecies.

Patrice

Re: Downgrading a module without any question
llandale - Mon Mar 28 15:01:29 EDT 2011

phenri - Mon Mar 28 11:06:56 EDT 2011
You are right that I am trying to FORCE people to enter a PR# to any changes they do. We have our own custom Save DXL that will update the Change Reason of each modified/deleted/undeleted object when a user is saving a module.

It might be appropriate here to mention this DOORS Client customisation was already done by another company from which we bought the IP of a certified project. So we have inherited this cutomisation and it did not work correctly in our own DOORS environement, therefore we had to get into it and modify it.

After I fixed and ported every DXL correctly, I started to see some holes and design deficiencies and tried to fix them the best I can, hence my 3 posts on this forum.

Even though I am trying to change these DXLs the least possible, I am willing to try better ways to do the same things, like trigger by exemple, if it fixes these deficinecies.

Patrice

Maybe there are two of these threads but I seem to recall replying, but don't see it above.

A pre-save-attr trigger may get what you want; and now that I think of it a post-module-open trigger that detects "shared" or "edit" mode may also get you there; forcing the user to enter your PR et tal on some form.

Lots of folks seem to favor monkeying with the deployed DOORS code (which is mostly DXL), but in my distributed environment (100s of doors clients) it doesn't seem reasonable to even try.

  • Louie